> as long as those working on clients can reach an agreement on how to move forward. That has proven, though, to be a pickle in the past.
I _think_ this is because we probably need to start thinking about three different aspects to the ecosystem and document them out:
- Specifications (_as they are now_)
- Server recommendations (_e.g: Timeline, yarnd, etc_)
- Client recommendations (_e.g: jenny, tt, tt2, twet, etc_)
> what is twtxt for you?
For me Twtxt is just the underlying format that Yarn.social builds upon ๐
Range
requests, but opted instead to just archive/rotate our feeds periodically ๐
There really isn't much point in having a feed in reverse chronological order, except (_maybe?_) so a human read view the new twts at the top of the file?! ๐คฃ_
.
(s) / dot(s) like @eapl.me are valid? ๐ค Or nicks even? ๐ค
----
Regex core subset (portable across languages):
Character sets
โข a matches โaโ
โข [a-z] any lowercase
โข [a-zA-Z0-9] alphanumeric
โข [^ab] any char but a or b
Repetition (applies to the preceding atom)
โข ? zero or one
โข * zero or more
โข + one or more
Groups
โข (ab)+ matches โabโ, โababโ, โฆ
โข Capture for extract/substitute via $1 or \1
Operators
โข foo|bar = foo or bar
โข ^ start anchor
โข $ end anchor
Ignore nonโportable shortcuts: \w, ., {n}, *?, lookarounds.
#regex101=
> I am up to increase the length of a twtxt, though.
Recall what we had this set to for this pod? ๐ง
https://movq.de/v/f0c0e1e38c/
Now itโs getting greener:
https://movq.de/v/24e62315ef/
[](https://movq.de/v/24e62315ef/IMG_20250421_071652.jpg%2Dsmall.jpg)
@<kate https://yarn.girlonthemoon.xyz/user/kat/twtxt.txt> Glad you think so! ๐ My goal with Yarn.social has always been to provide the best (_best that I can anyway!_) truly decentralised (_slow_) social experience that uses the Twtxt format under the hood ๐
Something is swallowing it.
- Sharing small posts
- Sharing links
- Sharing media
- Having long conversations
- Voting on topics, opinions or decisions
- RSVPing to virtual or physical events
yarnd
does for Youtube/Spotify/whatever embedding. Plus anyone can participate, even if they don't really have a client that understand it, it's just text with some "syntax" afterall.
- Gin
- Echo
- Chi
yarnd
UI/UX experience (_for those that use it_) and as "client" features (_not spec changes_). The two ideas are quite simple:- Voting -- a way to cast, collect a vote on a decision, topic or opinion.
- RSVP -- a way to "rsvp" to a virtual (_pr physical_) event.
Both would use "plain text" on top of the way we already use Twtxt today and clients would render an appropriate UI/UX._
https://third-bit.com/2025/04/18/a-dollar-a-minute/
# url
in your feed to be https://
๐
{
...
# Layer 4 Reverse Proxy
layer4 {
# Gopher
0.0.0.0:70 {
route {
proxy <internal_ip>:70
}
}
# IRC (TLS)
0.0.0.0:6697 {
route {
proxy <internal_ip>:6697
}
}
}
}
url
is http://
but he actually hosts a https://
feed with redirects. so things get a bit weird ๐ข